Activation of remote devices in a networked system

ABSTRACT

The present disclosure is generally directed to the generation of voice-activated data flows in interconnected network. The voice-activated data flows can include input audio signals that include a request and are detected at a client device. The client device can transmit the input audio signal to a data processing system, where the input audio signal can be parsed and passed to the data processing system of a service provider to fulfill the request in the input audio signal. The present solution is configured to conserve network resources by reducing the number of network transmissions needed to fulfill a request.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of priority under 35 U.S.C. § 120 as a continuation-in-part of U.S. patent application Ser. No. 16/107,617, filed Aug. 21, 2018, which is a continuation of U.S. patent application Ser. No. 16/064,961 filed Jun. 21, 2018, which is a U.S. National Stage under 35 U.C.S. § 371 of International Patent Application No. PCT/US2018/031451, filed on May 7, 2018 and designating the United States. The foregoing applications are hereby incorporated by reference in their entirety.

BACKGROUND

Excessive network transmissions, packet-based or otherwise, of network traffic data between computing devices can prevent a computing device from properly processing the network traffic data, completing an operation related to the network traffic data, or timely responding to the network traffic data. The excessive network transmissions of network traffic data can also complicate data routing or degrade the quality of the response if the responding computing device is at or above its processing capacity, which may result in inefficient bandwidth utilization. The excessive network transmissions can occur when multiple network transmissions are used to clarify or request additional information in response to a first network transmission.

SUMMARY

According to at least one aspect of the disclosure, a system to generate voice-activated threads in a networked computer environment can include a data processing system. The data processing system can include one or more processors and memory. The data processing system can execute a natural language processor (“NLP”), a remote application launcher, and an action handler component. The data processing system can receive, by the NLP component, a first input audio signal detected by a sensor of a first client computing device. The data processing system can parse, by the NLP component, the first input audio signal to identify a first request and a first entity. The data processing system can determine, by the action handler component, a plurality of candidate service provider devices. Each of the plurality of candidate service provider devices can be configured to fulfill the first request. Each of the plurality of candidate service provider device can be associated with a respective application installed on the first client computing device. The data processing system can select, by the action handler component, a service provider device from the plurality of candidate service provider devices. The data processing system can generate, by the remote application launcher, a digital component. The digital component can include an indication of the application associated with the service provider device and the first entity. The digital component can be configured to launch the application associated with the service provider device when executed by the first client computing device to fulfill the first request. The data processing system can transmit, by the action handler component, the digital component to the first client computing device in response to the first input audio signal.

According to at least one aspect of the disclosure, a method to generate voice-activated threads in a networked computer environment can include receiving, by an NLP component executed by a data processing system, a first input audio signal detected by a sensor of a first client computing device. The method can include parsing, by the NLP component, the first input audio signal to identify a first request and a first entity. The method can include determining, by an action handler component executed by the data processing system, a plurality of candidate service provider devices. Each of the plurality of candidate service provider devices can be configured to fulfill the first request. Each of the plurality of candidate service provider device can be associated with a respective application installed on the first client computing device. The method can include selecting, by the action handler component, a service provider device from the plurality of candidate service provider devices. The method can include generating, by a remote application launcher executed by the data processing system, a digital component. The digital component can include an indication of the application associated with the service provider device and the first entity. The digital component can be configured to launch the application associated with the service provider device when executed by the first client computing device to fulfill the first request. The method can include transmitting, by the action handler component, the digital component to the first client computing device in response to the first input audio signal.

According to at least one aspect of the disclosure, a system to generate voice-activated threads in a networked computer environment can include a data processing system. The data processing system can execute an NLP component and an action handler component. The data processing system can receive a first input audio signal that is detected by a sensor of a first client computing device. The data processing system can parse the first input audio signal to identify a first request. The data processing system can select a first action data structure based on the first request. The first action data structure can be associated with a first service provider device. The data processing system can transmit a first audio-based input request to the first client based at least on a field in the first action data structure. The data processing system can receive a second input audio signal detected by the sensor of the first client computing device that is generated in response to the first audio-based input request. The data processing system can parse the second input audio signal to identify a response entity in the second input audio signal. The data processing system can expand the response entity based on an expansion policy that is associated with the first client computing device. Expanding the response entity can include converting the response entity into format associated with the field in the first action data structure. The data processing system can populate the expanded response entity into the field of the first action data structure. The data processing system can transmit the first action data structure to the first service provide to fulfill the first request.

According to at least one aspect of the disclosure, a method to generate voice-activated threads in a networked computer environment can include receiving a first input audio signal that is detected by a sensor of a first client computing device. The method can include parsing the first input audio signal to identify a first request. The method can include selecting a first action data structure based on the first request. The first action data structure can be associated with a first service provider device. The method can include transmitting a first audio-based input request to the first client based at least on a field in the first action data structure. The method can include receiving a second input audio signal detected by the sensor of the first client computing device that is generated in response to the first audio-based input request. The method can include parsing the second input audio signal to identify a response entity in the second input audio signal. The method can include expanding the response entity based on an expansion policy that is associated with the first client computing device. Expanding the response entity can include converting the response entity into format associated with the field in the first action data structure. The method can include populating the expanded response entity into the field of the first action data structure. The method can include transmitting the first action data structure to the first service provide to fulfill the first request.

Each aspect can optionally include one or more of the following features. Parsing, by the natural language processor component, the first input audio signal to identify a second entity; expanding, by the action handler component executed by the data processing system, the second entity based on an expansion policy associated with the first client computing device and into a format associated with a field of the digital component; generating, by the action handler component, the digital component to include the expanded second entity in the field of the digital component. Parsing, by the natural language processor component, the first input audio signal to identify a second entity; and determining, by the action handler component, the second entity cannot be expanded based on an expansion policy associated with the first client computing device. Transmitting, by the action handler component, an audio-based input request to the first client computing device to request an updated entity. The digital component may be configured to populate a field of the application associated with the service provider device with the first entity when executed by the first client computing device. Measuring, by the action handler component, a network latency between the data processing system and each of the plurality of candidate service provider devices; and selecting, by the action handler component, the service provider device from the plurality of candidate service provider devices based at least on the network latency between the data processing system and each of the plurality of candidate service provider devices. Selecting, by the action handler component, the service provider device from the plurality of candidate service provider devices based at least a performance of each of the plurality of candidate service provider devices. Selecting, by the action handler component, the service provider device from the plurality of candidate service provider devices based at least a preference associated with the first client computing device. Receiving, by the natural language processor component, a second input audio signal detected by the sensor of the first client computing device, the second input audio signal comprising an indication of the service provider device; and selecting, by the action handler component, the service provider device from the plurality of candidate service provider devices based at least on the indication of the service provider device. Receiving, by the natural language processor component, a second input audio signal detected by the sensor of the first client computing device; parsing, by the natural language processor component, the second input audio signal to identify a second request and a second entity; determining, by the action handler component, the service provider device is configured to fulfill the second request; generating, by the action handler component, a first action data structure based on the second request and comprising the second entity; and transmitting, by the action handler component, the first action data structure to the service provider device.

According to at least one aspect of the disclosure, a system to generate threads in a networked computer environment can include a data processing system executing a natural language processor component and an action handler component. The data processing system can receive a first input audio signal detected by a sensor of a client computing device. The data processing system can parse the first input audio signal to identify a first request. The data processing system can select a service provider device configured to fulfill the first request and an action data structure including a form definition that can indicate parameters required for the fulfillment of the request. The data processing system can identify an open slot of a dialog frame based on a node graph generated based on the form definition indicating the parameters required for the fulfillment of the request. The data processing system can generate a first dialog candidate based on the open slot of the dialog frame. The data processing system can transmit the first dialog candidate to the client computing device. The data processing system can receive a second input audio signal detected by the sensor of the client computing device in response to rendering the first dialog candidate at the client computing device. The data processing system can parse the second input audio signal to identify a parameter. The data processing system can store the parameter into the open slot of the dialog frame. The data processing system can transmit the action data structure to the service provider device to fulfill the first request.

According to at least one aspect of the disclosure, a method to generate threads in a networked computer environment can include receiving, by a natural language processor component, a first input audio signal detected by a sensor of a client computing device. The method can include parsing, by the natural language processor component, the first input audio signal to identify a first request. The method can include selecting, by an action handler component, a service provider device configured to fulfill the first request and an action data structure that can include a form definition indicating parameters required for the fulfillment of the request. The method can include identifying, by the action handler component, an open slot of a dialog frame based on a node graph generated based on the form definition indicating the parameters required for the fulfillment of the request. The method can include generating, by the action handler component, a first dialog candidate based on the open slot of the dialog frame. The method can include transmitting, by the action handler component, the first dialog candidate to the client computing device. The method can include receiving, by the natural language processor component, a second input audio signal detected by the sensor of the client computing device in response to rendering the first dialog candidate at the client computing device. The method can include parsing, by the natural language processor component, the second input audio signal to identify a parameter. The method can include storing, by the action handler component, the parameter into the open slot of the dialog frame. The method can include transmitting, by the action handler component, the action data structure to the service provider device to fulfill the first request.

These and other aspects and implementations are discussed in detail below. The foregoing information and the following detailed description include illustrative examples of various aspects and implementations and provide an overview or framework for understanding the nature and character of the claimed aspects and implementations. The drawings provide illustration and a further understanding of the various aspects and implementations and are incorporated in and constitute a part of this specification.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements. For purposes of clarity, not every component may be labeled in every drawing. In the drawings:

FIG. 1 illustrates block diagram of an example system to authenticate computing devices, in accordance with an example of the present disclosure.

FIG. 2 illustrates a block diagram of an example method to generate voice-activated threads in the system illustrated in FIG. 1, in accordance with an example of the present disclosure.

FIG. 3 illustrates a block diagram of example data flows between components of the system illustrated in FIG. 1, in accordance with an example of the present disclosure.

FIG. 4 illustrates a block diagram of an example method to generate voice-activated threads in the system illustrated in FIG. 1, in accordance with an example of the present disclosure.

FIG. 5 illustrates a block diagram of example data flows between components of the system illustrated in FIG. 1, in accordance with an example of the present disclosure.

FIG. 6 illustrates a block diagram of an example method to generate threaded dialogs in a networked computer environment, in accordance with an example of the present disclosure.

FIG. 7 illustrates a block diagram of example data flows between components of the system in illustrated in FIG. 1, in accordance with an example of the present disclosure.

FIGS. 8-10 illustrate example graphs that can be generated based on the dialog frame, in accordance with examples of the present disclosure.

FIG. 11 illustrates a block diagram of an example computer system that can be used in the system illustrated in FIG. 1, in accordance with an example of the present disclosure.

DETAILED DESCRIPTION

Following below are more detailed descriptions of various concepts related to, and implementations of, methods, apparatuses, and systems to generate voice-activated data flows in interconnected network. The various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways.

The present disclosure is generally directed to the generation of voice-activated data flows in interconnected networks. The voice-activated data flows can include input audio signals that include a request and are detected at a client device. The client device can transmit the input audio signal to a data processing system, where the input audio signal can be parsed and passed to the data processing system of a service provider to fulfill the request in the input audio signal. Voice-activated systems can result in excessive data transmissions because one or more of the data processing systems may not be able to parse or understand the entities or terms in the input audio signals. For example, because of the conversational nature of the voice-activated system, users can often provide conversational-style answers that can be vague or unclear when removed from context. For example, when placing an order with a voice-driven (and hands free) digital assistant device, the data processing system of the service provider may receive an input audio signal from the digital assistant device that includes the statement “order a coffee from the coffee shop near my house.” The service provider's data processing system may understand that the phrase “near my house” is a location entity; however, the service provider's data processing system may not be able to convert the phrase into a specific location or the address of a specific coffee shop. This can result in wasted computational resources as the service provider's data processing system transmits follow up requests to the digital assistant device to request clarifying or additional input audio signals.

Systems and methods of the present technical solution enable a reduction in reducing computing resource utilization, and network bandwidth by reducing the number of network transmissions required to complete voice-based requests. The present solution can enable the digital assistant to automatically convert unclear terms into terms that can be processed by the service provider's data processing system, which can reduce the number of follow up input audio signals required to complete a request. For example, the present solution can enable the digital assistant to convert the term “home” into a specific address prior to transmitting the term to the service provider's data processing system, such that “123 Main St.” can be transmitted to the service provider's data processing system rather than the term “home.”

The present solution can also increase the privacy of the end user. For example, the end user can approve of transmitting an address to the service provider, a third-party. However, the end user may not wish to allow the third-party to know that the provided location is the end user's home address. The present solution can enable the digital assistant to convert the term “home” (or other protected term) into formatted data (e.g., a specific address), which the third party does not know is the user's home. The present solution can address problems associated with third-party service providers interacting with a user using a voice-based interface and can overcome technical challenges associated with allowing third-party service providers to operate together with a voice-based system.

FIG. 1 illustrates an example system 100 to generate voice-activated threads in a networked computer environment. The system 100 can include a data processing system 102. The data processing system 102 can communicate with one or more of a digital component provider device 106 (e.g., content provider device), client computing devices 104, or service provider devices 160 via a network 105. The network 105 can include computer networks such as the Internet, local, wide, metro, or other area networks, intranets, satellite networks, and other communication networks such as voice or data mobile telephone networks. The network 105 can be used to access information resources such as web pages, web sites, domain names, or uniform resource locators that can be presented, output, rendered, or displayed on at least one computing device 104, such as a laptop, desktop, tablet, digital assistant, personal digital assistant, smartwatch, wearable device, smart phone, portable computer, or speaker. For example, via the network 105 a user of the client computing device 104 can access information, data, or services provided by digital component provider devices 106 or the service provider devices 160. The client computing device 104 may or may not include a display. For example, the client computing device 104 may include limited types of user interfaces, such as a microphone and speaker (e.g., the client computing device 104 can include a voice-drive or audio-based interface). The primary user interface of the computing device 104 can include a microphone and speaker.

The network 105 can include or constitute a display network, e.g., a subset of information resources available on the internet that are associated with a content placement or search engine results system, or that are eligible to include third party digital components. The network 105 can be used by the data processing system 102 to access information resources such as web pages, web sites, domain names, or uniform resource locators that can be presented, output, rendered, or displayed by the client computing device 104. For example, via the network 105 a user of the client computing device 104 can access information or data provided by the digital component provider device 106.

The network 105 may be any type or form of network and may include any of the following: a point-to-point network, a broadcast network, a wide area network, a local area network, a telecommunications network, a data communication network, a computer network, an ATM (Asynchronous Transfer Mode) network, a SONET (Synchronous Optical Network) network, a SDH (Synchronous Digital Hierarchy) network, a wireless network, and a wireline network. The network 105 may include a wireless link, such as an infrared channel or satellite band. The topology of the network 105 may include a bus, star, or ring network topology. The network may include mobile telephone networks using any protocol or protocols used to communicate among mobile devices, including advanced mobile phone protocol (“AMPS”), time division multiple access (“TDMA”), code-division multiple access (“CDMA”), global system for mobile communication (“GSM”), general packet radio services (“GPRS”), or universal mobile telecommunications system (“UMTS”). Different types of data may be transmitted via different protocols, or the same types of data may be transmitted via different protocols.

The system 100 can include at least one data processing system 102. The data processing system 102 can include at least one logic device such as a computing device having a processor to communicate via the network 105, for example, with the computing device 104, service provider device 160, or the digital component provider device 106. The data processing system 102 can include at least one computation resource, server, processor, or memory. For example, the data processing system 102 can include a plurality of computation resources or servers located in at least one data center. The data processing system 102 can include multiple, logically-grouped servers and facilitate distributed computing techniques. The logical group of servers may be referred to as a data center, server farm, or a machine farm. The servers can also be geographically dispersed. A data center or machine farm may be administered as a single entity, or the machine farm can include a plurality of machine farms. The servers within each machine farm can be heterogeneous: one or more of the servers or machines can operate according to one or more type of operating system platform.

Servers in the machine farm can be stored in high-density rack systems, along with associated storage systems, and located in an enterprise data center. For example, consolidating the servers in this way may improve system manageability, data security, the physical security of the system, and system performance by locating servers and high-performance storage systems on localized high-performance networks. Centralization of all or some of the data processing system 102 components, including servers and storage systems, and coupling them with advanced system management tools, allows more efficient use of server resources, which saves power and processing requirements and reduces bandwidth usage.

The client computing device 104 can include, execute, interface, or otherwise communicate with one or more of at least one local digital assistant 134, at least one sensor 138, at least one transducer 140, at least one audio driver 142, or at least one display 144. The sensor 138 can include, for example, a camera, an ambient light sensor, proximity sensor, temperature sensor, accelerometer, gyroscope, motion detector, GPS sensor, location sensor, microphone, video, image detection, or touch sensor. The transducer 140 can include or be part of a speaker or a microphone. The audio driver 142 can provide a software interface to the hardware transducer 140. The audio driver 142 can execute the audio file or other instructions provided by the data processing system 102 to control the transducer 140 to generate a corresponding acoustic wave or sound wave. The display 144 can include one or more hardware or software component configured to provide a visual indication or optical output, such as a light emitting diode, organic light emitting diode, liquid crystal display, laser, or display.

The local digital assistant 134 can include or be executed by one or more processors, logic array, or memory. The local digital assistant 134 can detect a keyword and perform an action based on the keyword. The local digital assistance 134 can be an instance of the remote digital assistance component 112 executed at the data processing system 102 or can perform any of the functions of the remote digital assistance component 112. The local digital assistant 134 can filter out one or more terms or modify the terms prior to transmitting the terms as data to the data processing system 102 (e.g., remote digital assistant component 112) for further processing. The local digital assistant 134 can convert the analog audio signals detected by the transducer 140 into a digital audio signal and transmit one or more data packets carrying the digital audio signal to the data processing system 102 via the network 105. The local digital assistant 134 can transmit data packets carrying some or all of the input audio signal responsive to detecting an instruction to perform such transmission. The instruction can include, for example, a trigger keyword or other keyword or approval to transmit data packets comprising the input audio signal to the data processing system 102.

The local digital assistant 134 can perform pre-filtering or pre-processing on the input audio signal to remove certain frequencies of audio. The pre-filtering can include filters such as a low-pass filter, high-pass filter, or a bandpass filter. The filters can be applied in the frequency domain. The filters can be applied using digital signal processing techniques. The filter can be configured to keep frequencies that correspond to a human voice or human speech, while eliminating frequencies that fall outside the typical frequencies of human speech. For example, a bandpass filter can be configured to remove frequencies below a first threshold (e.g., 70 Hz, 75 Hz, 80 Hz, 85 Hz, 90 Hz, 95 Hz, 100 Hz, or 105 Hz) and above a second threshold (e.g., 200 Hz, 205 Hz, 210 Hz, 225 Hz, 235 Hz, 245 Hz, or 255 Hz). Applying a bandpass filter can reduce computing resource utilization in downstream processing. The local digital assistant 134 on the computing device 104 can apply the bandpass filter prior to transmitting the input audio signal to the data processing system 102, thereby reducing network bandwidth utilization. However, based on the computing resources available to the computing device 104 and the available network bandwidth, it may be more efficient to provide the input audio signal to the data processing system 102 to allow the data processing system 102 to perform the filtering.

The local digital assistant 134 can apply additional pre-processing or pre-filtering techniques such as noise reduction techniques to reduce ambient noise levels that can interfere with the natural language processor. Noise reduction techniques can improve accuracy and speed of the natural language processor, thereby improving the performance of the data processing system 102 and manage rendering of a graphical user interface provided via the display 144.

The client computing device 104 can be associated with an end user that enters voice queries as audio input into the client computing device 104 (via the sensor 138 or transducer 140) and receives audio (or other) output from the data processing system 102 or digital component provider device 106 to present, display, or render to the end user of the client computing device 104. The digital component can include a computer-generated voice that can be provided from the data processing system 102 or digital component provider device 106 to the client computing device 104. The client computing device 104 can render the computer-generated voice to the end user via the transducer 140 (e.g., a speaker). The computer-generated voice can include recordings from a real person or computer-generated language. The client computing device 104 can provide visual output via a display device 144 communicatively coupled to the computing device 104.

The end user that enters the voice queries to the client computing device 104 can be associated with multiple client computing devices 104. For example, the end user can be associated with a first client computing device 104 that can be a speaker-based digital assistant device, a second client computing device 104 that can be a mobile device (e.g., a smartphone), and a third client computing device 104 that can be a desktop computer. The data processing system 102 can associate each of the client computing devices 104 through a common login, location, network, or other linking data. For example, the end user may log into each of the client computing devices 104 with the same account user name and password.

The client computing device 104 can receive an input audio signal detected by a sensor 138 (e.g., microphone) of the computing device 104. The input audio signal can include, for example, a query, question, command, instructions, or other statement provided in a spoken language. The input audio signal can include an identifier or name of a third-party (e.g., a digital component provider device 106) to which the question or request is directed. For example, the query can include the name of the subscription-based music service (an example digital component provider device 106) in the input audio signal in order to instruct the data processing system 102 to provide the request to the specified subscription-based music service. For example, the input audio signal can include “Play my music playlist on XYZ Music Service.” The music service can provide the songs associated with the playlist to the client computing device 104 through the network 105 or to the data processing system 102, which can provide the songs associated with the playlist to the client computing device 104 through the network 105.

The client computing device 104 can include, execute, or be referred to as a digital assistant device. The digital assistant device can include one or more components of the computing device 104. The digital assistant device can include a graphics driver that can receive display output from the data processing system 102 and render the display output on display 132. The graphics driver can include hardware or software components that control or enhance how graphics or visual output is displayed on the display 144. The graphics driver can include, for example, a program that controls how the graphic components work with the rest of the computing device 104 (or digital assistant). The local digital assistant 134 can filter the input audio signal to create a filtered input audio signal, convert the filtered input audio signal to data packets, and transmit the data packets to a data processing system comprising one or more processors and memory.

The digital assistant device can include an audio driver 142 and a speaker component (e.g., transducer 140). The pre-processor component 140 can receive an indication of the display output and instruct the audio driver 142 to generate an output audio signal to cause the speaker component (e.g., transducer 140) to transmit an audio output corresponding to the indication of the display output.

The system 100 can include, access, or otherwise interact with at least digital component provider device 106. The digital component provider device 106 can include one or more servers that can provide digital components to the client computing device 104 or data processing system 102. The digital component provider device 106 or components thereof can be integrated with the data processing system 102 or executed at least partially by the data processing system 102. The digital component provider device 106 can include at least one logic device such as a computing device having a processor to communicate via the network 105, for example with the computing device 104, the data processing system 102, or the digital component provider device 106. The digital component provider device 106 can include at least one computation resource, server, processor, or memory. For example, the digital component provider device 106 can include a plurality of computation resources or servers located in at least one data center.

A digital component provider device 106 can provide audio, visual, or multimedia-based digital components for presentation by the client computing device 104 as an audio output digital component or visual output digital component. The digital component can be or include a digital content. The digital component can be or include a digital object. The digital component can include subscription-based content or pay-for content. A digital component can include a plurality of digital content items. For example, a digital component can be a data stream from a streaming music service (e.g., the digital component provider device 106). The streamed digital component can include multiple songs as different digital content items. The digital components can include or can be digital movies, websites, songs, applications (e.g., smartphone or other client device applications), or other text-based, audio-based, image-based, or video-based content.

The digital component provider device 106 can provide the digital components to the client computing device 104 via the network 105 and bypass the data processing system 102. The digital component provider device 106 can provide the digital component to the client computing device 104 via the network 105 and data processing system 102. For example, the digital component provider device 106 can provide the digital components to the data processing system 102, which can store the digital components and provide the digital components to the client computing device 104 when requested by the client computing device 104.

The data processing system 102 can include at least one computation resource or server. The data processing system 102 can include, interface, or otherwise communicate with at least one interface 110. The data processing system 102 can include, interface, or otherwise communicate with at least one remote digital assistant component 112. The remote digital assistant component 112 can include, interface, or otherwise communicate with at least one NLP component 114, at least one direct action handler component 135, and a least one remote application launcher 116. The data processing system 102 can include, interface, or otherwise communicate with at least one digital component selector 120. The data processing system 102 can include, interface, or otherwise communicate with at least one data repository 124. The at least one data repository 124 can include or store, in one or more data structures or databases, deep links 126, policies 128, templates 130, or content data 132. The data repository 124 can include one or more local or distributed databases, and can include a database management

The components of the data processing system 102 can each include at least one processing unit or other logic device such as a programmable logic array engine or module configured to communicate with the database repository or database 124. The components of the data processing system 102 can be separate components, a single component, or part of multiple data processing systems 102. The system 100 and its components, such as a data processing system 102, can include hardware elements, such as one or more processors, logic devices, or circuits.

The data processing system 102 can include an interface 110. The interface 110 can be configured, constructed, or operational to receive and transmit information using, for example, data packets. The interface 110 can receive and transmit information using one or more protocols, such as a network protocol. The interface 110 can include a hardware interface, software interface, wired interface, or wireless interface. The interface 110 can facilitate translating or formatting data from one format to another format. For example, the interface 110 can include an application programming interface (“API”) that includes definitions for communicating between various components, such as software components.

The data processing system 102 can include an application, script, or program installed at the client computing device 104, such as a local digital assistant 134 to communicate input audio signals to the interface 110 of the data processing system 102 and to drive components of the client computing device to render output audio signals or visual output. The data processing system 102 can receive data packets, a digital file, or other signals that include or identify an input audio signal (or input audio signals). The computing device 104 can detect the audio signal via the transducer 140 and convert the analog audio signal to a digital file via an analog-to-digital converter. For example, the audio driver 142 can include an analog-to-digital converter component. The pre-processor component 140 can convert the audio signals to a digital file that can be transmitted via data packets over network 105.

The remote digital assistant component 112 of the data processing system 102 can execute or run an NLP component 114 to receive or obtain the data packets including the input audio signal detected by the sensor 138 of the computing device 104. The data packets can provide a digital file. The NLP component 114 can receive or obtain the digital file or data packets comprising the audio signal and parse the audio signal. For example, the NLP component 114 can provide for interactions between a human and a computer. The NLP component 114 can be configured with techniques for understanding natural language and enabling the data processing system 102 to derive meaning from human or natural language input. The NLP component 114 can include or be configured with techniques based on machine learning, such as statistical machine learning. The NLP component 114 can utilize decision trees, statistical models, or probabilistic models to parse the input audio signal. The NLP component 114 can perform, for example, functions such as named entity recognition (e.g., given a stream of text, determine which items in the text map to names, such as people or places, and what the type of each such name is, such as person, location (e.g., “home”), or organization), natural language generation (e.g., convert information from computer databases or semantic intents into understandable human language), natural language understanding (e.g., convert text into more formal representations such as first-order logic structures that a computer module can manipulate), machine translation (e.g., automatically translate text from one human language to another), morphological segmentation (e.g., separating words into individual morphemes and identify the class of the morphemes, which can be challenging based on the complexity of the morphology or structure of the words of the language being considered), question answering (e.g., determining an answer to a human-language question, which can be specific or open-ended), or semantic processing (e.g., processing that can occur after identifying a word and encoding its meaning in order to relate the identified word to other words with similar meanings).

The NLP component 114 can convert the input audio signal into recognized text by comparing the input signal against a stored, representative set of audio waveforms (e.g., in the data repository 124) and choosing the closest matches. The set of audio waveforms can be stored in data repository 124 or other database accessible to the data processing system 102. The representative waveforms are generated across a large set of users, and then may be augmented with speech samples from the user. After the audio signal is converted into recognized text, the NLP component 114 matches the text to words that are associated, for example via training across users or through manual specification, with actions that the data processing system 102 can serve. The NLP component 114 can convert image or video input to text or digital files. The NLP component 114 can process, analyze, or interpret image or video input to perform actions, generate requests, or select or identify data structures.

The data processing system 102 can receive image or video input signals, in addition to, or instead of, input audio signals. The data processing system 102 can process the image or video input signals using, for example, image interpretation techniques, computer vision, a machine learning engine, or other techniques to recognize or interpret the image or video to convert the image or video to a digital file. The one or more image interpretation techniques, computer vision techniques, or machine learning techniques can be collectively referred to as imaging techniques. The data processing system 102 (e.g., the NLP component 114) can be configured with the imaging techniques, in addition to, or instead of, audio processing techniques.

The NLP component 114 can obtain the input audio signal. From the input audio signal, the NLP component 114 can identify at least one request, at least one trigger keyword corresponding to the request, and one or more entities. The request can indicate intent, digital components, or subject matter of the input audio signal. The trigger keyword can indicate a type of action likely to be taken. For example, the NLP component 114 can parse the input audio signal to identify at least one request to leave home for the evening to attend dinner and a movie. The trigger keyword can include at least one word, phrase, root or partial word, or derivative indicating an action to be taken. The intent can be an expressly stated intent that identifies an action to be taken or an agent to interact with. For example, the input audio signal that includes an express intent for a car service can be “Ok, get me a car service to the go to the movies.” The intent can also be derived or not expressly stated. For example, in the input audio signal that includes “Ok, I want to go to the movies” does not expressly request a car service, but the NLP component 114 can derive the intent. For example, the trigger keyword “go” or “to go to” from the input audio signal can indicate a need for transport. In this example, the input audio signal (or the identified request) does not directly express an intent for transport, however the trigger keyword indicates that transport is an ancillary action to at least one other action that is indicated by the request.

The NLP component 114 can parse the input audio signal to identify, determine, retrieve, or otherwise obtain the request and the trigger keyword. For instance, the NLP component 114 can apply a semantic processing technique to the input audio signal to identify the trigger keyword or the request. The NLP component 114 can apply the semantic processing technique to the input audio signal to identify a trigger phrase that includes one or more trigger keywords, such as a first trigger keyword and a second trigger keyword. For example, the input audio signal can include the sentence “Play my favorite song.” The NLP component 114 can determine that the input audio signal includes a trigger keyword “play.” The NLP component 114 can determine that the request is for the end user's favorite song (a digital component). The NLP component 114 can identify an application identifier or a digital component provider device 106 identifier in the input audio signal. The application identifier or digital component provider device 106 identifier can indicate which application or digital component provider device 106 the end user would like to fill the request.

The data processing system 102 can execute or run an instance of the direct action handler component 135. The direct action handler component 135 can execute scripts or programs based on input received from the NLP component 114. The service provider device 160 can provide the scripts or programs. The service provider device 160 can make the scripts or programs available to the data processing system 102 through an API or webhooks. The direct action handler component 135 can determine parameters or responses to input fields and can package the data into an action data structure. The action data structure can be provided to the data processing system 102 through an API or webhooks. The direct action handler component 135 can transmit the action data structure to a service provider device 160 for fulfillment or the data processing system 102 can fulfill the action data structure.

The direct action handler component 135 can generate or select, based on the request or the trigger keyword identified in an input audio signal, data structures for the actions of a thread or conversation. Based on the request parsed by the NLP component 114, the direct action handler component 135 can determine to which of a plurality of service provider computing devices 160 the message should be sent. The direct action handler component 135 can determine that the input audio signal includes a request for an explicit service provider device 160 (e.g., “Order a car with Car Service XYZ,” where the request specifically requests the request be fulfilled by Car Service XYZ) or can select from a plurality of service provider devices 160 can fulfill the request. The direct action handler component 135 can package the request into an action data structure for transmission as a message to a service provider computing device 160. The action data structure can include information for completing the request. The information can be data that the service provider device 160 uses to complete the request. Continuing the above example for a car service request, the information can include a pick up location and a destination location. The direct action handler component 135 can retrieve a template 130 from the repository 124 to determine which fields to include in the action data structure. The direct action handler component 135 can retrieve content from the repository 124 to obtain information for the fields of the data structure. The direct action handler component 135 can populate the fields from the template with that information to generate the data structure. The direct action handler component 135 can also populate the fields with data from the input audio signal or previous input audio signals. The templates 130 can be standardized for categories of service providers or can be standardized for specific service providers. For example, ride sharing service providers can use the following standardized template 149 to create the data structure: {client_deviceidentifier; authentication_credentials; pick_uplocation; destination_location; no_passengers; service_level}.

The direct action handler component 135 can be configured to expand responses or entities contained in the responses. The direct action handler component 135 can expand entities that the NLP component 114 identifies in the input audio signal. The direct action handler component 135 can expand the entities to convert the entities into a format that the service provider device 160 requires for a given field of its action data structures. The entities can include information that may be ambiguous or unclear to a service provider device 160. For example, when the service provider device 160 requested a street address, the end user may provide an entity that is the proper name of a location or business. The direct action handler component 135 can automatically generate the expanded entity based on content or preferences the data processing system 102 received from the client computing device 104. The direct action handler component 135 can generate the expanded entity based on content or preferences the data processing system 102 requests from the client computing device 104 in a subsequent audio-based input request. For example, the data processing system 102 can receive an input audio signal that includes “Ok, request a car service to pick me up at home.” The NLP component 114 can identify the term “home” as an entity that the service provider device 160 cannot recognize. For example, the NLP component 114 can identify “home” as a location entity; however, the location field in the action data structure can require a street address, city, state, and zip code. In this example, the “home” location entity is not in the format requested by the service provider device 160. If the end user of the client computing device 104 previously provided the data processing system 102 with the end user's home address, the direct action handler component 135 can expand “home” into the format requested by field of the service provider device's action data structure (e.g., {street_address:“123 Main St.”, city:“Anytown”, state:“CA”}). If the end user did not previously provide the data processing system 102 with the end user's home address, the data processing system 102 can generate and transmit an audio-based input request that requests the end user indicate a specific address rather than “home.” Expanding the entity prior to transmitting the entity to the service provider device 160 can reduce the number of required network transmission because the service provider device 160 may not need to request clarifying or additional information after receiving the unexpanded entity.

The direct action handler component 135 can expand the entities based on an expansion policy 128 that is associated with the client computing device 104 that provided the input audio signal. The expansion policy 128 can indicate whether the digital component provider device 128 has permission to expand or convert the identified entity. For example, and continuing the above example, the direct action handler component 135 can, based on the expansion policy 128, determine whether the direct action handler component 135 has access to convert the location entity “home” into a specific address.

The direct action handler component 135 can generating input requests based at least on the interface type of the client computing device 104 and one or more fields of an action data structure for a service provider device 160. The data processing system 102 can gather information and populate the fields of a service provider device's action data structure by transmitting a series of input requests to the client computing device 104. For example, the data processing system 102 can initiate a conversation-based data exchange with the client computing device 104. The content of the input request can be defined by the service provider device 160. For example, the service provider device 160 can define the dialog of the input requests that prompt the end user of the client computing device 104 to provide inputs to the data processing system 102 (via the client computing device 104) such that the direct action handler component 135 can populate the fields of the action data structure. The service provider device 160 may have to develop multiple instances of the dialogs to account for the different types of client computing devices 104 that may interact with the data processing system 102. The different types of client computing device 104 may include different types of interfaces, which can also be referred to as surfaces. For example, a first client computing device 104 can include a voice-only interface, and a second client computing device 104 can include a screen-based interface.

The direct action handler component 135 can enable the service provider device 160 to provide only the action data structure the service provider device 160 needs populated to fulfill a request. The direct action handler component 135, rather than the service provider device 160, can generate or define the input requests based on the fields in the action data structure. The direct action handler component 135 can generate or define the input requests based on the fields in the action data structure and a device type or interface type associate with the client computing device 104. The input requests can be data objects that can include text, images, audio, videos, or any combination thereof. When executed or rendered by the client computing device 104, the client computing device 104 generates output signals (via a screen, speaker, or other interface). For example, for a client computing device 104 that includes a touch screen, rendering the input request can cause the client computing device 104 to display input boxes a user can select via the touch screen. For a client computing device 104 that includes only a voice-based interface, rendering the input request can cause the client computing device 104 to present audio prompts to the user via the client computing device's speakers.

The direct action handler component 135 can populate one or more fields of the action data structure without generating an input request that is transmitted to the client computing device 104. The direct action handler component 135 can populate one or more fields of the action data structure with content previously provide by the client computing device 104 (or end user thereof). For example, if the action data structure requests an address that the end user previously provided either while setting up the client computing device 104 (or an account associated with the client computing device 104) or in a prior input audio signal.

The action handler component 135 can dynamically generate dialog frames. Based on the dialog frames, the action handler component 135 can generate dialog candidates that are transmitted to the client computing device 104 to request parameters used in the fulfilment of the requests parsed by the NLP component 114 from input audio signals. By generating the dialog frames and dialog candidates therefrom, the data processing system 102 can dynamically generate dialog for a conversation-based interaction with the data processing system 102 rather than having the dialog generated and provided by the service provider device 160. This can reduce network usage because service provider device 160 only transmits a data structure indicating required parameters for fulfilment of a request rather than transmitting full dialog. Dynamically generating the dialog frames can also reduce computational requirements because the data processing system 102 can only generate dialog candidates to request parameters from the data processing system 102 that have not yet been provided by the data processing system 102 rather than following a static schema that can generate requests for parameters that have already been provided by the data processing system 102.

For each action or request that the service provider device 160 can fulfil, the service provider device 160 can transmit an action data structure template that includes a form definition for a given action or request. The form definition can include an indication of the parameters that the service provider device 160 needs to fulfil the action or request. For example, a service provider device 160 providing a ride share service can provide an action data structure template with a form definition that indicates that a pickup location parameter, a destination location parameter, and a car type parameter are required by the service provider device 160 for the service provider device 160 to fulfil a request for a car. The form definition can be in a JSON format, XLM format, of other schema-based format.

For each parameter, the form definition can include a name field to describe the parameter, a slot field to store the value of the parameter, a requirement flag to indicate whether the parameter is an optional parameter, and a type field to indicate the expected or required data type or format of the parameter. Responsive to the identification of a request in an input audio signal, the action handler component 135 can identify or select a service provider device 160 that can fulfill the request and an action data structure associated with the selected service provider device 160 for the fulfilment of the request. The action handler component 135 can identify parameters with empty slots. The action handler component 135 can generate candidate dialogs that can include a prompt to request the parameter from the user.

The data processing system 102 can execute or run an instance of the remote application launcher 116. The remote application launcher 116 can identify, via the NLP component 114, keywords, tokens, terms, concepts, intents, or other information in the digital file or prior audio input to identify one or more applications stored on or executable by the client computing device 104 to fulfill the identified intent. The remote application launcher 116 can parse log files of application installs provided by the client computing device 104 to determine which applications are installed on the client computing device. For example, the NLP component 114 can determine that the intent for the input audio signal “Ok, request a car to take me to the airport” is to request a car service. When the client computing device 104 installs an application configured to fulfill one or more intents, the application can register with the data processing system 102. For example, the application can provide the data processing system 102 with a manifest file that indicates which intents the application can fulfill. The data processing system 102 can store an indication of the application and intent in the database in association with a unique identifier associated with the client computing device 104. Based on determining the intent of the request, the remote application launcher 116 can search the manifests stored in association with the unique identifier for the client computing device 104 and select an application that is configured to fulfill the intent.

The remote application launcher 116 can generate a deep link. The remote application launcher 116 can transmit the deep link to the client computing device 104. The deep link can cause the client computing device 104 to launch or invoke the application that the remote application launcher 116 selected to fulfill the intent. The data processing system 102 can store templates of the deep-links associated with the applications executed by the client computing device 104 as deep links 126 in the repository 124. The remote application launcher 116 can populate the deep links with entities identified in the input audio signal, expanded entities, or other content the client computing device 104 (or user thereof) previously provided the data processing system 102. Once launched, the application can populate one or more fields in the application with the information or data populated into the deep links. For example, continuing the above example, the remote application launcher 116 can populate the deep link with the end users home address and the airport address. Execution of the deep link by the application can, for example, cause the car service application to automatically populate the start location field with the end user's home address and the destination field with the address of the airport.

The data processing system 102 can execute or run an instance of the digital component selector 120. The digital component selector 120 can select a digital component that includes text, strings, characters, video files, image files, or audio files that can be processed by the client computing device 104 and presented to the user via the display 144 or the transducer 140 (e.g., speaker). Deep links can be an example digital component. Action data structures can be an example digital component.

The digital component selector 120 can select a digital component that is responsive to the request identified by the NLP component 114 in the input audio signal. The digital component selector 120 can select which digital component provider device 106 should or can fulfill the request and can forward the request to the digital component provider device 106. For example, the data processing system 102 can initiate a session between the digital component provider device 106 and the client computing device 104 to enable the digital component provider device 106 to transmit the digital component to the client computing device 104. The digital component selector 120 can request digital component from the digital component provider device 106. The digital component provider device 106 can provide digital components to the data processing system 102, which can store the digital components in the data repository 124. Responsive to a request for a digital component, the digital component selector 120 can retrieve the digital component from the data repository 124.

The digital component selector 120 can select multiple digital components via a real-time content selection process. The digital component selector 120 can score and rank the digital components and provide multiple digital components to the output merger component 120 to allow the output merger component 120 to select the highest ranking digital component. The digital component selector 120 can select one or more additional digital components that are transmitted to a second client computing device 104 based on an input audio signal (or keywords and requests contained therein). The one or more additional digital components can be transmitted to the second client computing device 104 as part of or in addition to the authorization request. For example, if the input audio signal from the first client computing device 104 includes a request for a digital component from a first digital component provider device 106, the digital component selector 120 can select one or more digital components that correspond to one or more related digital component provider devices 106. In one illustrative example, the input audio signal can include a request to start a streaming music to a first client computing device 104. The digital component selector 120 can select additional digital components (e.g., ads) that are associated with a different digital component provider device 106. The data processing system 102 can include the additional digital components in the authorization request to the second client computing device 104. The additional digital components can inform an end user of additional or related digital component provider devices 106 that could fulfill the request from the first client computing device 104.

The digital component selector 120 can provide the digital component selected in response to the request identified in the input audio signal to the computing device 104, or local digital assistant 134, or application executing on the computing device 104 for presentation. Thus, the digital component selector 120 can receive the content request from the client computing device 104, select, responsive to the content request, a digital component, and transmit, to the client computing device 104, the digital component for presentation. The digital component selector 120 can transmit, to the local digital assistant 134, the selected digital component for presentation by the local digital assistant 134 itself or a third-party application executed by the client computing device 104. For example, the local digital assistant 134 can play or output an audio signal corresponding to the selected digital component.

The data repository 124 can store deep links 126 that can be stored in one or more data structures or data files. The deep links 126 can be stored in a table or database. The deep links 126 can include links, pointers, references, or other address or location information of an application that can be executed by the client computing device 104. A deep link to an application can refer to a uniform resource locator or hyperlink that links to a specific resource, web content, application, or view within an application. The deep link can include the information used to point to a particular resource or application, launch an application, or populate predetermined fields within the application. Deep links can include uniform resource identifiers (“URI”) that links to a specific location within a mobile application in addition to launching the application. For example, opening, selecting, or executing a deep link on the client computing device 104 can cause the client computing device 104 to open an application associated with the digital component provider device 106. The deep link fully or partially pre-populates a registration or sign-up form within the opened application. In this example, to register for the subscription service offered by the digital component provider device 106, the end user may need to only review the information entered into the form and then select a confirmation icon located on the loaded application page. The deep links 126 data structure can include a hash table that maps application names or views of an application to a deep link.

The data repository 124 can store expansion policies 128 that can be stored in one or more data structures or data files. The expansion policies 128 can indicate what data, information, or entities can be expanded. The data processing system 102 can store a different expansion policy 128 for each of the client computing devices 104 associated with the data processing system 102.

The data repository 124 store content data 132 that can include, for example, digital components provided by a digital component provider device 106 or obtained or determined by the data processing system 102 to facilitate content selection. The content data 132 can include, for example, digital components (or digital component object) that can include, for example, a content item, an online document, audio, images, video, multimedia content, or third-party content. The content data 132 can include digital components, data, or information provided by the client computing devices 104 (or end user thereof). For example, the content data 132 can include user preferences, user information stored by the user, or data from prior input audio signals.

The service provider device 160 can execute, include, or access a service provider NLP component 161 and a service provide interface 162. The service provider NLP component 161 can be an instance of or perform the functions of the NLP component 114. For example, the data processing system 102 can forward an input audio signal to the service provider device 160 and the service provider NLP component 161 can process the input audio signal. The service provider interface 162 can be an instance of the interface 110. The service provider interface 162 can be software interface or a hardware interface. The service provider interface 162 can be an API or set of webhooks.

FIG. 2 illustrates a block diagram of an example method 200 to generate voice-activated threads in a networked computer environment. The method can include receiving an input audio signal (ACT 202). The method 200 can include parsing the input audio signal (ACT 204). The method 200 can include selecting an action data structure (ACT 206). The method 200 can include expanding a response entity (ACT 208). The method can include populating the action data structure (ACT 210). The method 200 can include transmitting the digital component (ACT 212).

The method 200 can include can include receiving an input signal (ACT 202). The method can include receiving, by an NLP component executed by a data processing system, the input signal. The input signal can be an input audio signal that is detected by a sensor at a first client device and transmitted to the data processing system. The sensor can be a microphone of the first client device. For example, a digital assistant component executed at least partially by a data processing system that includes one or more processors and memory can receive the input audio signal. The input audio signal can include a conversation facilitated by a digital assistant. The conversation can include one or more inputs and outputs. The conversation can be audio based, text based, or a combination of audio and text. The input audio signal can include text input, or other types of input that can provide conversational information. The data processing system can receive the audio input for a session corresponding to the conversation.

The method 200 can include parsing the input signal (ACT 204). The NLP component of the data processing system can parse the input signal to identify a request. The NLP component can identify at least one entity in the input signal. The request can be an intent or request that can be fulfilled by one or more service provider devices. The request can be a part of a conversational phrase. For example, the request can be “Ok, order a car to take me home.” The entities identified by the NLP component can be phrases or terms in the request that map to input fields or types the service provider device requests when fulfilling a request. For example, the service provider device providing the car service may request a current location input field and a destination input field. Continuing the above example, the NLP component can map the term “home” to the destination input field.

The method 200 can include selecting an action data structure (ACT 206). The data processing system can select the action data structure based on the request parsed from the input signal. The data processing system can select the action data structure based on the service provider device that can fulfill the request. The action data structure can be a data structure or object that is created by the service provider device. The service provider device can provide the action data structure to the data processing system. The action data structure can indicate fields, data, or information that the service provider device uses to fulfill requests. The service provider device can flag one or more of the fields to request that the data processing system expand the entity returned for that field. When a field is flagged for expansion, the data processing system can design and generate conversation-based data exchanges with the client computing device 104 to retrieve information or data for the flagged field rather than the service provider device 160 designing the conversation-based data exchange.

The method 200 can include expanding the response entity (ACT 208). The data processing system can determine the entity mapped to the input field needs to be expanded if the entity is not in a format specified by the service provider device. Continuing the above example, the NLP component can determine “home” is the entity mapped to a destination. The direct action handler component can determine to update the action data structure to include the entity “home” in a destination field. The direct action handler component can determine the format of the response entity does not match the format of the destination field. For example, the destination field can have the format of an object that requests a street address, city, state, and zip code. Detecting a mismatch between the format of the response entity and the format of the field, the data processing system can expand the entity to a street address, city, state, and zip code format. For example, the data processing system can look up the address the end user provided the data processing system as the end user's “home” address. The data processing system can check that the format of the response entity does not match the format of the destination field and rather than forwarding the response to the service provider device, the data processing system can expand the entity. The data processing system can automatically expand the entity because the data processing system knows that the response provided by the user is not in the correct format and the response could cause the agent of the service provider device to fail. For example, the service provider device may not be able to understand the entity “home.” If the data processing system determines the entity is not in the correct format and the data processing system cannot expand the entity into the proper format, the data processing system can transmit an input request to the client computing device that can prompt the user of the client computing device for additional information. The data processing system can expand the entity based on an expansion policy. The expansion policy can indicate whether the data processing system has permission to expand the term or can indicate what end user or client computing device provided data can be included in an expanded entity.

The data processing system can expand the entity based on a request from a service provider device. For example, the data processing system can generate a first action data structure with the unexpanded entity. The data processing system can transmit the first action data structure to the service provider device for processing to fulfill the request. The service provider device can return the action data structure (or a portion thereof) to the data processing system if the service provider device cannot process or understand the data in on or more of the action data structure's fields. For example, the service provider device can attempt to process the “home” entity in the destination field and then request the data processing system expand the “home” entity after the service provider device determines that it cannot process or understand the entity.

The method 200 can include populating the action data structure (ACT 210). The direct action handler component can populate the action data structure with the expanded entity. The direct action handler component can populate the action data structure with the entity. For example, the action data structure can be an object into which the entity or expanded entity is stored. Populating the action data structure can also be referred to update the action data structure.

The method 200 can include transmitting the action data structure (ACT 212). The data processing system can transmit the populated action data structure to the service provider device. Upon receipt of the action data structure, the service provider device can fulfill the request or request additional information from the data processing system or client computing device.

FIG. 3 illustrates a block diagram of an example data flows between components of the system 100 illustrated in FIG. 1. FIG. 3 illustrates the data flows during an example implementation of the method 200 illustrated in FIG. 3. The example includes the expansion of an entity identified in an input signal. The example can include transmitting one or more data flows between the data processing system 102, client computing device 104, and the service provider device 160.

At a first time point, the service provider device 160 can transmit a first data flow 301 to the data processing system 102. The first data flow 301 can include an action data structure template. The action data structure template can indicate to the data processing system 102 what fields the service provider device 160 may require to fulfill one or more intents or services. For example, the first data flow 301 can include an action data structure template for requesting a car service. In the example illustrated in FIG. 3, the action data structure template includes {origin: “ ”, dest: “ ”}, which indicates that the service provider device 160 may need an origin location and a destination location when a car service is requested.

The client computing device 104 can transmit a data flow 302 to the data processing system 102 to invoke a service provided by the service provider device 160. The data flow 302 can include an input audio signal. The input audio signal can, in the example illustrated in FIG. 3, include the phrase “Ok, order a car service.” Based on the invocation of the data flow 302, the data processing system 102 can transmit an input request, such as an audio-based input request, to the client computing device 104 in data flow 303. Rendering or presentation of the input request illustrated in FIG. 3 at the client computing device 104 can cause the client computing device 104 to present through a speaker at the client computing device 104 “Where would you like to go?” The end user can respond to the input request. For example, the end user can speak “from my office to the airport” in response to the input request. The client computing device 104 can via the sensor 138 (e.g., a microphone) detect the end user's response, digitize the response, and transmit the response to the data processing system 102 as an input audio signal within the data flow 304.

The data processing system 102 can parse the input audio signal and identify one or more response entities in the input audio signal. The data processing system 102 can identify response entities that are vague. The response entities can be terms or phrases that the NLP component 114 maps to one or more fields of the action data structure. For example, as illustrated in FIG. 3, the action data structure includes two fields that each require locations as inputs. The data processing system 102 can map the term “office” and “airport” as response entities that map to the formats associated with the fields of the action data structure. Based on an expansion policy associated with the client computing device 104, the data processing system 102 can expand the response entities into a format required by the fields of the action data structure. In the example illustrated in FIG. 3, the “office” response entity is expanded to “123 Main St.” and the term “airport” is expanded to “323 5th St.” The action data structure with the expanded response entities can be transmitted to the service provider device 160 in the data flow 305.

FIG. 4 illustrates a block diagram of an example method 400 to generate voice-activated threads in a networked computer environment. The method can include receiving an input audio signal (ACT 402). The method 400 can include parsing the input audio signal (ACT 404). The method 400 can include determining a plurality of candidate service provider devices (ACT 406). The method 400 can include selecting a service provider device (ACT 408). The method 400 can include generating a digital component (ACT 410). The method 400 can include transmitting the digital component (ACT 412).

As set forth above, and also referring to FIG. 1, among others, the method 400 can include can include receiving an input signal (ACT 402). The method can include receiving, by an NLP component executed by a data processing system, the input signal. The input signal can be an input audio signal that is detected by a sensor at a first client device and transmitted to the data processing system. The sensor can be a microphone of the first client device. For example, a digital assistant component executed at least partially by a data processing system that includes one or more processors and memory can receive the input audio signal. The input audio signal can include a conversation facilitated by a digital assistant. The conversation can include one or more inputs and outputs. The conversation can be audio based, text based, or a combination of audio and text. The input audio signal can include text input or other types of input that can provide conversational information. The data processing system can receive the audio input for a session corresponding to the conversation.

The method 400 can include parsing the input signal (ACT 404). The NLP component of the data processing system can parse the input signal to identify a request and at least one entity. The request can be an intent or request that can be fulfilled by one or more service provider devices. The request can be a conversational phrase. For example, the request can be “Ok, order a car to take me home.” The entities identified by the NLP component can be phrases or terms in the request that map to input fields or types the service provider device requests when fulfilling a request. For example, the service provider device providing the car service may request a current location input field and a destination input field. Continuing the above example, the NLP component can map the term “home” to the destination input field.

The method 400 can include determining or identifying a plurality of candidate service provider devices (ACT 406). Each of the plurality of candidate service provider devices can be configured to fulfill the request identified in the input audio signal. Each of the candidate service provider devices can be associated with a respective application that is installed on the client computing device. For example, each of the candidate service provider devices can be car service providers that provide applications that an end user can install on their client computing device (e.g., smart phone) to request a car from the car service provider. The data processing system can maintain a database that indicates which applications are installed on the client computing device. For example, the applications can be installed through an application store provided by the data processing system and the data processing system can update an entry in the data repository when applications are installed or removed from the client computing device. Determining or identifying which service provider device can fulfill the request can include identifying a data processing system that can include a plurality of devices, identifying a webhook address of the service provider device, an IP address of the service provider device, a domain name of the service provider device, or an API of the service provider device.

If the data processing system determines that the no application associated with one of the candidate service provider devices is installed on the client computing device, the data processing system can select a service provider device from the candidate service provider devices and generate an action data structure rather than a digital component (e.g., deep link). The data processing system can populate the action data structure with entities or expanded entities identified in the input signal. The data processing system can transmit the action data structure to the selected service provider device to fulfill the request.

The method 400 can include selecting a service provider device (ACT 408). The data processing system can select the service provider device from the plurality of service provider devices. The data processing system can select the service provider device based on a network latency between the data processing system and each of the candidate service provider devices. For example, if the latency between a specific service provider device and the data processing system is high, the data processing system can determine that the candidate service provider device is experiencing network or other computational problems and that new request should not be transmitted to the specific candidate service provider device. The data processing system can select the service provider device from the candidate service provider devices based on a selection made by an end user of the client computing device. For example, the data processing system can transmit an input request to the client computing device that when rendered by the client computing device presents a list of the candidate service provider devices. The end user can provide a selection to the data processing system through an input audio signal transmitted from the client computing device. The data processing system can select the service provider device based on a performance of the candidate service provider devices. The performance can be a computational performance or a service rating. For example, the service rating can be generated by user reviews after interacting with the specific service provider device. The data processing system can select the service provider device based on which candidate service provider device has the highest service rating.

The method 400 can include generating a digital component (ACT 410). The method 400 can include generating, by the action handler component, a digital component that can include an indication of the application associated with the service provider device. The digital component can also include the first entity. The digital component, when executed or rendered by the client computing device, can cause the client computing device to launch the application associated with the service provider device. The digital component can be a deep link. The digital component can be an action data structure. The application can be used to fulfill the request in the input audio signal. For example, and continuing the above example, when executed, the digital component can launch the car requesting application on the end user's smart phone. The digital component can include one or more fields. The direct action handler component can populate the entity or an expanded version of the entity into one or more fields of the digital component.

The method 400 can include transmitting the digital component to the first client computing device (ACT 412). The data processing system can transmit the digital component to the client computing device in response to receiving the input audio signal. When the client computing device receives the digital component (e.g., a deep link), the digital component can be rendered on a screen of the client computing device. The end user can activate the client computing device by selecting the deep link. Activation of the deep link can cause the client computing device to open the application associated with the selected service provider device. The deep link can also populate fields (e.g., text fields) of the open application with the entities populated into the digital component.

FIG. 5 illustrates a block diagram of example data flows between components of the system 100 in illustrated in FIG. 1. FIG. 5 illustrates the data flows during an example implementation of the method 400 illustrated in FIG. 4. The example includes the expansion of an entity identified in an input signal and the fulfillment of an intent with deep links. The data flows can be between a client computing device 104, a data processing system 102, a first service provider device 160(1), and a second service provider device 160(2).

As illustrated in FIG. 5, and also referring to FIG. 1 among others, the client computing device 104 can transmit a first input audio signal to the data processing system 102 in a first data flow 501. In the example illustrated in FIG. 5, the input audio signal includes the phrase “Ok, get me a car service home.” The data processing system 102 receive the data flow and determine that the input audio signal includes a request or intent for a car service. The data processing system 102 can access a log file that indicates which applications are installed on the client computing device 104. The log file can also indicate which intents or request types each of the applications can fulfill. For example, the client computing device 104 can include a first application that is associated with the service provider device 160(1), which can be a first car service provider and a second application that is associated with the service provider device 160(2), which can be a second car service provider. The data processing system 102 can select one of the service provider device 160(1) and the service provider device 160(2) to fulfill the request in the input audio signal.

The data processing system 102 can select a deep link template that is associated with the selected service provider device 160 from the deep links 126 stored in the data repository 124. For example, in the example illustrated in FIG. 5, the data processing system 102 can select the service provider device 160(1). The data processing system 102 can generate the deep link and populate the fields of the deep link with entities or expanded entities the NLP component 114 identified in the input audio signal. For example, the entity “home” in the input audio signal can be expanded to “123 Main St.” The data processing system 102 can transmit the deep link to the client computing device 104 in data flow 502. When the client computing device 104 renders or executes the deep link, the deep link can cause the client computing device 104 to open or execute the application identified in the deep link. For example, the deep link transmitted to the client computing device 104 in the data flow 502 can cause the client computing device 104 to open the application associated with the service provider device 160(1).

Execution of the deep link can also cause the data from the fields of the deep link to be automatically populated into one or more fields of the open application. For example, when the client computing device 104 opens the application associated with the service provider device 160(1), the deep link can cause “123 Main St.” to be populated into the destination field of the application. The client computing device 104, via the application associated with the service provider device 160(1), can send a data flow 503 to the service provider device 160(1) to fulfill the request in the input audio signal of the data flow 501.

The data processing system can generate voice-activated threads in a networked computer environment. The data processing system can receive a first input audio signal that is detected by a sensor of a first client computing device. The data processing system can parse the first input audio signal to identify a first request. The data processing system can select a first action data structure based on the first request. The first action data structure can be associated with a first service provider device. The data processing system can transmit a first audio-based input request to the first client based at least on a field in the first action data structure. The data processing system can receive a second input audio signal detected by the sensor of the first client computing device that is generated in response to the first audio-based input request. The data processing system can parse the second input audio signal to identify a response entity in the second input audio signal. The data processing system can expand the response entity based on an expansion policy that is associated with the first client computing device. Expanding the response entity can include converting the response entity into format associated with the field in the first action data structure. The data processing system can populate the expanded response entity into the field of the first action data structure. The data processing system can transmit the first action data structure to the first service provide to fulfill the first request.

FIG. 6 illustrates a block diagram of an example method 600 to generate threaded dialogs in a networked computer environment. The method 600 can include receiving an input signal (ACT 602). The method 600 can include parsing the input signal (ACT 604). The method 600 can include selecting a service provider and an action data structure (ACT 606). The method 600 can include identifying an open slot (ACT 608). The method 600 can include generating a dialog candidate (ACT 610) and transmitting the dialog candidate (ACT 612). The method 600 can include receiving an input signal (ACT 614) and parsing the input signal (ACT 616). The method 600 can include storing a parameter (ACT 618). The method 600 can include transmitting the action data structure (ACT 620).

As set forth above and also referring to FIG. 1, among others, the method 600 can include receiving an input signal (ACT 602). The method 600 can include receiving, by the natural language processor component, a first input signal detected by a sensor of a client computing device. The input signal can be an input audio signal that is detected by a sensor at a first client device and transmitted to the data processing system. The sensor can be a microphone of the first client device. For example, a digital assistant component executed at least partially by a data processing system that includes one or more processors and memory can receive the input audio signal. The input audio signal can include a conversation facilitated by a digital assistant. The conversation can include one or more inputs (e.g., audio signals transmitted to the data processing system) and outputs (e.g., audio signals transmitted from the data processing system). The conversation and the input signal can be audio based, text based, or a combination of audio and text. The input audio signal can include text input or other types of input that can provide conversational information. The data processing system can receive the audio input for a session corresponding to the conversation.

Also referring to FIG. 7, among others, FIG. 7 illustrates the data processing system 102 receiving an input signal. FIG. 7 illustrates a block diagram of example data flows between components of the system 100 in illustrated in FIG. 1. FIG. 6 illustrates the data flows 703(1)-703(1) (collectively referred to as data flows 703) that can pass between the client computing device 104, the data processing system 102, and the service provider device 160. The data flow 703 be transmitted between the client computing device 104, the data processing system 102, and the service provider device 160 via the network 105. The client computing device 104 can generate a plurality of audio signals 702 (which can also be referred to as the input audio signals).

For example, as at ACT 602, the client computing device 104 can detect, via the sensor 138, audio signals that the client computing device 104 can digitize as audio signals 702(1). The client computing device 104 can transmit the audio signal 702(1) to the data processing system 102 in data flow 703(1).

The method 600 can include parsing the input signal (ACT 604). The method 600 can include parsing, by the NLP component, the first input audio signal to identify a first request. The NLP component of the data processing system can parse the input signal to identify a request and at least one entity. The request can be an intent or request that can be fulfilled by one or more service provider devices. The request can be a conversational phrase. For example, the request can be “Ok, order a car to take me home.” The entities identified by the NLP component can be phrases or terms in the request that map to input fields or types the service provider device requests when fulfilling a request. For example, the service provider device providing the car service may request a current location input field and a destination input field. Continuing the above example, the NLP component can map the term “home” to the destination input field.

The method 600 can include selecting a service provider and an action data structure (ACT 606). The service provider device can be configured to fulfill the request identified in the input audio signal. The data processing system 102 can select a service provider device 160 that is configured to or capable of fulling the request. The selection of the service provider device 160 can be based on an intent or action identified in the input signal. The service provider device 160 can be associated with an application that is installed on the client computing device. The data processing system can maintain a database that indicates which applications are installed on the client computing device. For example, the applications can be installed through an application store provided by the data processing system and the data processing system can update an entry in the data repository when applications are installed or removed from the client computing device. Determining or identifying which service provider device can fulfill the request can include identifying a data processing system that can include a plurality of devices, identifying a webhook address of the service provider device, an IP address of the service provider device, a domain name of the service provider device, or an API of the service provider device.

The method 600 can include selecting an action data structure. The action data structure can include a dialog frame. The action data structure can include a form definition from which the data processing system 102 can generate dialog frames. The dialog frame can be provided by the service provider device 160. The dialog frame can be a data structure that indicates which parameters the service provider device 160 requires to fulfill the request identified in the input signal. The dialog frame can indicate optional parameters for the fulfillment of a request. The dialog frame can be a data structure that includes a plurality of slots. Each slot can have a value and a type. Initially, the value for each of the slots can be empty or set to a default value. A slot in a first frame can be an instance of a second frame and can inherit slots and values from the second frame. For example, a first frame for a ride share service request can have a destination slot, which can link to a destination frame that includes slots for street number, street name, city, and zip code.

The action handler component 135 can dynamically generate the dialog frame based on the form definition provided by the service provider device 160. For each request that the service provider device 160 can fulfill, the service provider device 160 can provide the data processing system 102 with a form definition that can indicate the parameters that the service provider device 160 needs to fulfill the request. For example, if the service provider device 160 provides ride sharing services, the service provider device 160 can provide a form definition indicating that the service provider device 160 requires a destination location value and a pickup location value when fulfilling a request for a car. The form definition can indicate that some parameters, such as a car type value can be optional.

The method 600 can include identifying an open slot in the dialog frame (ACT 608). The action handler component 135 can generate a node graph to select the open slot. The graph can be a directed acyclic graph (DAG) that can include a plurality of nodes each linked together. The node graph can include parameter nodes that are associated with slots in the frame dialog, validation nodes, setup nodes, and fulfilment nodes. The nodes are described further in relation to FIGS. 8-10.

Parameter nodes can indicate a slot in the dialog frame. The nodes can be linked together to indicate a hierarchal relationship between the slots and values in the dialog frame. For example, the dialog frame provided by a service provider for retrieving a bank account balance can include an “account” slot and a “balance” slot. The “balance” slot can be dependent on the “account” slot because the balance cannot be known until an account is first selected. The action handler component 135 can generate a graph based on the dialog frame and can select the highest hierarchical node (and slot) that is open, empty, or includes a default value. For example, and continuing the above example, if the graph includes an empty balance node and an empty account node, the action handler component 135 can select to fill the empty account node (and thus account slot) before filling the balance node.

FIGS. 8-10 illustrate example graphs that can be generated based on the dialog frame. The graphs can include parameter nodes 802, fulfilment nodes 804, setup nodes 806, and validation nodes 808. The node graphs can be generated by the action handler component 135. The action handler component 135 can construct a node graph based on the dialog frame to determine for which parameters the action handler component 135 should next generate a dialog candidate. The parameter nodes 802 can correspond to open slots in the dialog frame and can correspond to the nodes of the node graphs that are configured to receive inputs. The fulfillment nodes 804 are the nodes of the node graph that can be called once all the parameter nodes 802 linked with the fulfillment node 804 is filled. The setup nodes 806 can block inputs from the client computing device 104 to later nodes in the node graph until the action handler component 135 receives setup instructions from the service provider device 160. For example, an example setup node 806 can require the client computing device 104 to authenticate with the service provider device 160. The node graphs can include validation nodes 808. The validation nodes 808 can indicate when the action handler component 135 should send the form state (or received parameters) to the service provider device 160 for validation.

FIG. 8 illustrates an example node graph 800. The node graph 800 includes three parameter nodes 802 that link to a fulfilment node 804. The node graph 800 indicates that the dialog frame includes three slots to be filled before the action data structure can be transmitted to the service provider device 160 for fulfilment. As illustrated in the node graph 800, each of the parameter nodes 802 are at the same hierarchical level and the action handler component 135 can generate a dialog candidate to request any of the parameters associated with the parameter nodes 802.

FIG. 9 illustrates an example node graph 900. The node graph 900 includes a setup node 806 at a top level, three parameter nodes 802 at a middle level, and a fulfilment node 804 at a bottom level. The action handler component 135 can generate a node graph similar to node graph 900, when the dialog frame requires the client computing device 104 authenticate with the service provider device 160 or the user to log into a service provided by the service provider device 160. For example, to request bank account information the user may have to authenticate with the service provider device 160 before the action handler component 135 can start filling slots of the dialog frame.

FIG. 10 illustrates an example node graph 1000. The node graph 1000 can include three parameter nodes 802 that can feed into a first validation node 808, a set of two parameter nodes 802 that can feed into a second validation node 808, and a parameter node 802 that feeds directly into the fulfilment node 804 along with the two validation nodes 808. The action handler component 135 can generate a node graph similar to the node graph 1000 when the dialog frame indicates that one or more of parameters should be validated by the service provider device 160. The node graph 1000 illustrates that three of the parameter nodes 802 must be fulfilled before the values of the parameter nodes 802 are validated. For example, making a reservation at a restaurant, the node graph can indicate that the action handler component 135 should collect the parameters: reservation time, party size, and restaurant name and then validate the parameters together with the service provider device 160. As illustrated in FIG. 10, a portion of the parameter nodes 802 can serve as inputs to validation nodes 808 and a portion of the parameter nodes 802 do not require validation and can serve as inputs directly to the fulfilment node 804.

Referring to FIG. 6, among others, the method 600 can include generating a dialog candidate (ACT 610). The action handler component 135 can generate the dialog candidate based on the open slot that was selected at ACT 608. The dialog candidate can be a text-based or audio-based prompt to provide the value for the open slot. For example, request can be for a car service and the action handler component 135 can determine that the open slot is a destination slot. The action handler component 135 can generate a dialog candidate of “where would you like to go?”

The method 600 can include transmitting the dialog candidate (ACT 612). The method 600 can include transmitting the dialog candidate to the client computing device 104. For example, and also referring to FIG. 7, the data processing system 102 can transmit the dialog candidate 701(1) to the client computing device 104 in the data flow 703(2). Once the client computing device 104 receives the dialog candidate 701(1), the client computing device 104 can render the dialog candidate 701(1) as an audio output via a speaker or as text on the display of the client computing device 104. Responsive to rendering the dialog candidate 701(1), the client computing device 104 can enter a response phase where the client computing device's sensor (e.g., microphone) is active to record a response from the user. The client computing device 104 capture the user response. The user response can be text-based (e.g., the user can type the response). The user response can be audio-based. For example, the client computing device 104 can capture an input audio signal as audio signal 702(2). The client computing device 104 can transmit the audio signal 702(2) to the data processing system 102 in the data flow 703(3).

The method 600 can include receiving an input signal (ACT 614). Also referring to FIG. 7, among others, the input signal can be an input audio signal (e.g., audio signal 702(2)) that is generated in response to a dialog candidate (e.g., dialog candidate 701(1)) begin rendered or received at the client computing device 104.

The method 600 can include parsing the input signal (ACT 616). The NLP component 114 can parse the input signal (e.g., the audio signal 702(2)) to identify a parameter in the input signal. For example, and continuing the above ride share request, in response to the dialog candidate “where would you like to go,” the data processing system 102 can receive an audio signal 702(2) that includes the utterance “123 Main Street.” The NLP component 114 can determine that “123 Main Street” is a destination and set “123 Main Street” to the parameter parsed from the input signal. The action handler component 135 can generate additional dialog candidates 701 to request additional parameters from the client computing device 104. For example, the action handler component 135 can generate a second dialog candidate 701(2) to request a second parameter from the client computing device 104.

The method 600 can include storing the parameter (ACT 618). The parameter can be stored into the open slot identified at ACT 608. The dialog frame with the parameter stored into the previously open slot can be referred to as an updated dialog frame. The action handler component 135 can save the updated dialog frame as a form state. The action handler component 135 can save the dialog frame as a form state each time the dialog frame is updated. The action handler component 135 can save the form state in association with an identifier of the client computing device 104 that transmitted the input signal and an identification of the service provider device 160 identified at ACT 606. The action handler component 135 can store the form state for a predetermined length of time. For example, the action handler component 135 can set the form state to expire after 1 minute, 5 minutes, 30 minutes, 1 day, 1 week, 1 month, 3 months, or any duration therein. Once the form state expires the action handler component 135 can delete or purge the form state from the data processing system 102.

Also referring to FIG. 7, among others, the data processing system 102 can transmit the form state to the service provider device 160 in data flow 703(4). The data processing system 102 can transmit the form state to the service provider device 160 to validate one or more parameters of the dialog frame, to update slots of the dialog frame, to add slots to the dialog frame, or to remove slots of the dialog frame. For example, if the request is to book a reservation at a given restaurant at 6:30 PM, a form state with a value of “6” in the “party size” slot and a value of “6:30 PM” in the “time” slot can be sent to the service provider device 160 for validation. The service provider device 160 can validate the “party size” slot and the “time” slot by determining whether the restaurant has an open table for 6 at 6:30 PM. If the restaurant does not, the service provider device 160 can invalidate the value in the party size slot or the time slot. Invalidating the value of a slot can include deleting the value, flagging the value as invalid, or replacing the invalid value with a value that is valid. For example, if the restaurant does not have a table for 6 at 6:30 PM but does have a table for 6 at 7 PM, the service provider device 160 could invalidate the time slot, flag the time slot as invalid, or replace the value “6:30 PM” in the time slot with the value of “7 PM.” The service provider device 160 can provide webhooks that enable the data processing system 102 to transmit the parameters to the service provider device 160 for validation.

The service provider device 160 can update one or more slots of a received form state prior to transmitting the updated form state back to the data processing system 102. For example, each slot of the form state can include an “option” field to indicate whether a value is required or not for the given slot. For example, the dialog frame and resulting form state for reserving a table at a restaurant can include a slot labeled “credit card” option field is initially set to yes indicating that a credit card number is optional and not required for the service provider device 160 to fulfill the request. The service provider device 160 can receive a form state where the “restaurant name” slot is “Joe's Restaurant.” The service provider device 160 can determine that Joe's Restaurant requires a credit card for holding a reservation and set the option field for the “credit card” slot to “no” to indicate that the field is not optional and that a credit card is required. The updated form state can be transmitted back to the data processing system 102 which can identify the “credit card” slot as an unfilled (e.g., open) and required slot and can generate a dialog candidate to request credit card information from the user.

The service provider device 160 can add or remove slots from the form state or can replace the form state with a different form state. For example, if the form state does not initial include a “credit card” slot and the service provider device 160 determines that Joe's Restaurant requires a credit card when making a reservation, the service provider device 160 could add a “credit card” slot to the form state with an empty value.

Still referring to FIG. 7, the data processing system 102 can generate a dialog candidate 701 each time the data processing system 102 receives an updated form state from the service provider device 160 or another conversational turn (e.g., an audio signal 702) from the client computing device 104 when the dialog frame includes open, required slots. For example, the based on receiving an updated form state, the data processing system 102 can generate a second dialog candidate 701 that is transmitted to the client computing device 104 in the data flow 703(5). The data processing system 102 can continue to transmit dialog candidates 701 to the client computing device 104 until each required slot of the dialog frame is filled.

The method 600 can include transmitting the action data structure (ACT 620). The method 600 can include transmitting the action data structure to the service provider device 160. The action data structure transmitted to the service provider device 160 can include the final form state after the last required slot of the dialog frame is filled. For example, and referring to FIG. 7, the audio signal 702(3), can include the parameter for the last open slot of the dialog frame. The data processing system 102 can receive the audio signal 702(3) in data flow 703(6) and identify the parameter in the audio signal 702(3). The action handler component 135 can fill the open slot in the dialog frame. The action handler component 135 can determine the dialog frame includes no empty required slots. The action handler component 135 can save the dialog frame as a form state and transmit the action data structure with the form state to the service provider device 160 in data flow 703(7). Responsive to receiving the action data structure, the service provider device 160 can fulfill the request parsed at ACT 604. The service provider device 160 can transmit a post execution template to the data processing system 102 in the data flow 703(8). The post execution template can include a confirmation that the request was fulfilled. The action handler component 135 can generate a dialog candidate 701(3) based on the post execution template, which can be transmitted to the data processing system 102 in data flow 703(9).

The method 600 can include saving the form state. The action handler component 135 can save the form state responsive to transmitting the action data structure to the service provider device 160. The action handler component 135 can save the form state in association with an identifier of the service provider device 160 and the client computing device 104. The action handler component 135 can set the form state to expire after a predetermined amount of time. If the data processing system 102 receives a second request from the client computing device 104 to be fulfilled by the same service provider device 160 that fulfilled a first request and the form state associated with the first request has not expired, the action handler component 135 can fill one or more slots of the dialog frame associated with the second request with the values from the form state associated with the first request.

For example, if the first request is for a car service to pick up the user at “123 Main Street” and drop off the user at “123 Park Ave” the action handler component 135 can save a form state after the action data structure with the above information is transmitted to the service provider device 160 of the car service provider. The form state can be saved as, for example {pick_up: “123 Main Street”, destination: “123 Park Ave”}. If before the form state expires, the data processing system 102 receives a second request from the client computing device 104 of “Ok, have the car service pick me up at 200 Main Street instead,” the action handler component 135 can determine that the second request is update the first request. In response to the second request, the action handler component 135 can select an action data structure and associated dialog frame to fulfill the request. The action handler component 135 can fill in “200 Main Street” (as parsed from input audio signal containing the second request) into the pickup location slot of the dialog frame and “123 Park Ave” (as retrieved from the first form state) into the destination slot of the dialog frame. As the dialog frame includes no more open slots, the action handler component 135 can save the dialog frame as a form state and transmit the form state to the service provider device 160 in an action data structure to update the first request. Saving the form states can save network and computational resources because parameters can be retrieved from past requests rather than requiring the data processing system 102 retransmit the parameters to the client computing device 104. Saving the form states can also enable coordination between fulfilment of different requests by different service providers. For example, the form state from a first request fulfilled by a first service provider device 160 can be used for fill parameters for a second request to be fulfilled by a second service provider device 160.

FIG. 11 is a block diagram of an example computer system 1100. The computer system or computing device 1100 can include or be used to implement the system 100, or its components such as the data processing system 102. The data processing system 102 can include an intelligent personal assistant or voice-based digital assistant. The computing system 1100 includes a bus 1105 or other communication component for communicating information and a processor 1110 or processing circuit coupled to the bus 1105 for processing information. The computing system 1100 can also include one or more processors 1110 or processing circuits coupled to the bus for processing information. The computing system 1100 also includes main memory 1115, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 1105 for storing information, and instructions to be executed by the processor 1110. The main memory 1115 can be or include the data repository 124. The main memory 1115 can also be used for storing position information, temporary variables, or other intermediate information during execution of instructions by the processor 1110. The computing system 1100 may further include a read-only memory (ROM) 1120 or other static storage device coupled to the bus 1105 for storing static information and instructions for the processor 1110. A storage device 1125, such as a solid-state device, magnetic disk or optical disk, can be coupled to the bus 1105 to persistently store information and instructions. The storage device 1125 can include or be part of the data repository 124.

The computing system 1100 may be coupled via the bus 1105 to a display 1135, such as a liquid crystal display, or active matrix display, for displaying information to a user. An input device 1130, such as a keyboard including alphanumeric and other keys, may be coupled to the bus 1105 for communicating information and command selections to the processor 1110. The input device 1130 can include a touch screen display 1135. The input device 1130 can also include a cursor control, such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor 1110 and for controlling cursor movement on the display 1135. The display 1135 can be part of the data processing system 102, the client computing device 104 or other component of FIG. 1, for example.

The processes, systems and methods described herein can be implemented by the computing system 1100 in response to the processor 1110 executing an arrangement of instructions contained in main memory 1115. Such instructions can be read into main memory 1115 from another computer-readable medium, such as the storage device 1125. Execution of the arrangement of instructions contained in main memory 1115 causes the computing system 1100 to perform the illustrative processes described herein. One or more processors in a multi-processing arrangement may also be employed to execute the instructions contained in main memory 1115. Hard-wired circuitry can be used in place of or in combination with software instructions together with the systems and methods described herein. Systems and methods described herein are not limited to any specific combination of hardware circuitry and software.

Although an example computing system has been described in FIG. 6, the subject matter including the operations described in this specification can be implemented in other types of digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.

For situations in which the systems discussed herein collect personal information about users, or may make use of personal information, the users may be provided with an opportunity to control whether programs or features that may collect personal information (e.g., information about a user's social network, social actions or activities, a user's preferences, or a user's location), or to control whether or how to receive content from a content server or other data processing system that may be more relevant to the user. In addition, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed when generating parameters. For example, a user's identity may be anonymized so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, postal code, or state level), so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about him or her and used by the content server.

The subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. The subject matter described in this specification can be implemented as one or more computer programs, e.g., one or more circuits of computer program instructions, encoded on one or more computer storage media for execution by, or to control the operation of, data processing apparatuses. Alternatively, or in addition, the program instructions can be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. While a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially generated propagated signal. The computer storage medium can also be, or be included in, one or more separate components or media (e.g., multiple CDs, disks, or other storage devices). The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

The terms “data processing system,” “computing device,” “component,” or “data processing apparatus” encompass various apparatuses, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations of the foregoing. The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures. For example, the interface 110, digital component selector 120, the direct action handler component 135, remote launcher application 116, or NLP component 114 and other data processing system 102 components can include or share one or more data processing apparatuses, systems, computing devices, or processors.

A computer program (also known as a program, software, software application, app, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program can correspond to a file in a file system. A computer program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs (e.g., components of the data processing system 102) to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatuses can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

The subject matter described herein can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described in this specification), or a combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system such as system 100 or system 1100 can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network (e.g., the network 105). The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some implementations, a server transmits data (e.g., data packets representing a digital component) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server (e.g., received by the data processing system 102 from the client computing device 104 or the digital component provider device 106).

While operations are depicted in the drawings in a particular order, such operations are not required to be performed in the particular order shown or in sequential order, and all illustrated operations are not required to be performed. Actions described herein can be performed in a different order.

The separation of various system components does not require separation in all implementations, and the described program components can be included in a single hardware or software product. For example, the NLP component 114, direct action handler component 135, remote launcher application 116, or the digital component selector 120, can be a single component, app, or program, or a logic device having one or more processing circuits, or part of one or more servers of the data processing system 102.

Having now described some illustrative implementations, it is apparent that the foregoing is illustrative and not limiting, having been presented by way of example. In particular, although many of the examples presented herein involve specific combinations of method acts or system elements, those acts and those elements may be combined in other ways to accomplish the same objectives. Acts, elements and features discussed in connection with one implementation are not intended to be excluded from a similar role in other implementations or implementations.

The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including” “comprising” “having” “containing” “involving” “characterized by” “characterized in that” and variations thereof herein, is meant to encompass the items listed thereafter, equivalents thereof, and additional items, as well as alternate implementations consisting of the items listed thereafter exclusively. In one implementation, the systems and methods described herein consist of one, each combination of more than one, or all of the described elements, acts, or components.

Any references to implementations or elements or acts of the systems and methods herein referred to in the singular may also embrace implementations including a plurality of these elements, and any references in plural to any implementation or element or act herein may also embrace implementations including only a single element. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements to single or plural configurations. References to any act or element being based on any information, act or element may include implementations where the act or element is based at least in part on any information, act, or element.

Any implementation disclosed herein may be combined with any other implementation or embodiment, and references to “an implementation,” “some implementations,” “one implementation” or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the implementation may be included in at least one implementation or embodiment. Such terms as used herein are not necessarily all referring to the same implementation. Any implementation may be combined with any other implementation, inclusively or exclusively, in any manner consistent with the aspects and implementations disclosed herein.

References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all the described terms. For example, a reference to “at least one of ‘A’ and ‘B ’ “can include only ‘A’, only ‘B’, as well as both ‘A’ and ‘B’. Such references used in conjunction with “comprising” or other open terminology can include additional items.

Where technical features in the drawings, detailed description or any claim are followed by reference signs, the reference signs have been included to increase the intelligibility of the drawings, detailed description, and claims. Accordingly, neither the reference signs nor their absence has any limiting effect on the scope of any claim elements.

The systems and methods described herein may be embodied in other specific forms without departing from the characteristics thereof. For example, the computing device 104 can generate the packaged data object and forward it to the third-party application when launching the application. The foregoing implementations are illustrative rather than limiting of the described systems and methods. Scope of the systems and methods described herein is thus indicated by the appended claims, rather than the foregoing description, and changes that come within the meaning and range of equivalency of the claims are embraced therein. 

1.-20. (canceled)
 21. A system to generate threads in a networked computer environment: a data processing system executing a natural language processor component and an action handler component to: receive, by the natural language processor component, a first input audio signal detected by a sensor of a client computing device; parse, by the natural language processor component, the first input audio signal to identify a first request; select, by the action handler component, a service provider device to fulfill the first request and an action data structure comprising a form definition that indicates parameters required for fulfillment of the first request; identify, by the action handler component, an open slot of a dialog frame based on a node graph, the node graph generated based on the form definition that indicates the parameters required for the fulfillment of the first request; generate, by the action handler component, a first dialog candidate based on the open slot of the dialog frame; transmit, by the action handler component, the first dialog candidate to the client computing device; receive, by the natural language processor component, a second input audio signal detected by the sensor of the client computing device in response to the first dialog candidate rendered at the client computing device; parse, by the natural language processor component, the second input audio signal to identify a parameter; store, by the action handler component, the parameter into the open slot of the dialog frame; and transmit, by the action handler component, the action data structure to the service provider device to fulfill the first request.
 22. The system of claim 21, comprising the action handler component to: store the action data structure with the parameter in the open slot of the dialog frame as a form state; transmit the form state to the service provider device for validation of the parameter; receive an updated form state; and update the action data structure based on the updated form state.
 23. The system of claim 21, comprising the action handler component to: transmit a form state comprising the parameter in the open slot of the dialog frame to the service provider device for validation by the service provider device; receive an updated form state that indicates the parameter in the open slot of the dialog frame is invalid; and generate a second dialog candidate based on the open slot of the dialog frame.
 24. The system of claim 21, comprising the action handler component to: store a form state comprising the parameter in the open slot based on transmitting the action data structure to the service provider device.
 25. The system of claim 21, comprising: store, by the action handler component and based on the transmission of the action data structure to the service provider device, a form state based on the first request; receive, by the natural language processor component, a third input audio signal detected by the sensor of the client computing device, the third input audio signal comprising a second request; select, by the action handler component, the service provider device configured to fulfill the second request and a second action data structure comprising associated with the second request; fill, by the action handler component, at least one slot of the second action data structure based on the form state based on the first request.
 26. The system of claim 21, comprising the action handler component to: identify each of a plurality of open slots in the dialog frame; and generate a respective dialog candidate for each of the plurality of open slots in the dialog frame.
 27. The system of claim 21, comprising a remote application launcher executed by the data processing system to: generate a digital component comprising an indication of an application associated with the service provider device and installed at the client computing device, the digital component configured to launch the application associated with the service provider device; and transmit the digital component to the client computing device.
 28. The system of claim 21, comprising: identify, by the action handler component, a second open slot of the dialog frame; generate, by the action handler component, a second dialog candidate based on the second open slot of the dialog frame; transmit, by the action handler component, the second dialog candidate to the client computing device; receive, by the natural language processor component, a third input audio signal detected by the sensor of the client computing device in response to rendering the second dialog candidate at the client computing device; parse, by the natural language processor component, the third input audio signal to identify an entity; expand, by the action handler component, the entity into a format associated with the second open slot of the dialog frame; and store, by the action handler component, the expanded entity into the second open slot of the dialog frame.
 29. The system of claim 28, comprising the action handler component to: expand the entity into the format associated with the second open slot of the dialog frame based on an expansion policy associated with the client computing device.
 30. The system of claim 21, comprising the action handler component to: convert the parameter into a format associated with the open slot of the dialog frame.
 31. A method to generate communication threads in a networked computer environment: receiving, by a natural language processor component executed by a data processing system, a first input audio signal detected by a sensor of a client computing device; parsing, by the natural language processor component, the first input audio signal to identify a first request; selecting, by an action handler component executed by the data processing system, a service provider device to fulfill the first request and an action data structure comprising a form definition indicating parameters required for fulfillment of the first request; identifying, by the action handler component, an open slot of a dialog frame based on a node graph, the node graph generated based on the form definition indicating the parameters required for the fulfillment of the first request; generating, by the action handler component, a first dialog candidate based on the open slot of the dialog frame; transmitting, by the action handler component, the first dialog candidate to the client computing device; receiving, by the natural language processor component, a second input audio signal detected by the sensor of the client computing device in response to rendering the first dialog candidate at the client computing device; parsing, by the natural language processor component, the second input audio signal to identify a parameter; storing, by the action handler component, the parameter into the open slot of the dialog frame; and transmitting, by the action handler component, the action data structure to the service provider device to fulfill the first request.
 32. The method of claim 31, comprising: storing, by the action handler component, the action data structure with the parameter in the open slot of the dialog frame as a form state; transmitting, by the action handler component, the form state to the service provider device for validation of the parameter; receiving, by the action handler component, an updated form state; and updating, by the action handler component, the action data structure based on the updated form state.
 33. The method of claim 31, comprising: transmitting, by the action handler component, a form state comprising the parameter in the open slot of the dialog frame to the service provider device for validation by the service provider device; receiving, by the action handler component, an updated form state indicating the parameter in the open slot of the dialog frame is invalid; and generating, by the action handler component, a second dialog candidate based on the open slot of the dialog frame.
 34. The method of claim 31, comprising: storing, by the action handler component, a form state comprising the parameter in the open slot based on transmitting the action data structure to the service provider device.
 35. The method of claim 31, comprising: storing, by the action handler component and based on transmitting the action data structure to the service provider device, a form state based on the first request; receiving, by the natural language processor component, a third input audio signal detected by the sensor of the client computing device, the third input audio signal comprising a second request; selecting, by the action handler component, the service provider device configured to fulfill the second request and a second action data structure comprising associated with the second request; filling, by the action handler component, at least one slot of the second action data structure based on the form state based on the first request.
 36. The method of claim 31, comprising: identifying, by the action handler component, each of a plurality of open slots in the dialog frame; and generating, by the action handler component, a respective dialog candidate for each of the plurality of open slots in the dialog frame.
 37. The method of claim 31, comprising: generating, by a remote application launcher, a digital component comprising an indication of an application associated with the service provider device and installed at the client computing device, the digital component configured to launch the application associated with the service provider device; and transmitting, by the remote application launcher, the digital component to the client computing device.
 38. The method of claim 31, comprising: identifying, by the action handler component, a second open slot of the dialog frame; generating, by the action handler component, a second dialog candidate based on the second open slot of the dialog frame; transmitting, by the action handler component, the second dialog candidate to the client computing device; receiving, by the natural language processor component, a third input audio signal detected by the sensor of the client computing device in response to rendering the second dialog candidate at the client computing device; parsing, by the natural language processor component, the third input audio signal to identify an entity; expanding, by the action handler component, the entity into a format associated with the second open slot of the dialog frame; and storing, by the action handler component, the expanded entity into the second open slot of the dialog frame.
 39. A system to generate threads in a networked computer environment: a data processing system executing a natural language processor component and an action handler component to: receive, by the natural language processor component, a first input audio signal detected by a sensor of a client computing device; parse, by the natural language processor component, the first input audio signal to identify a first request; select, by the action handler component, a service provider device to fulfill the first request and an action data structure that indicates parameters required for fulfillment of the first request; identify, by the action handler component, an open slot of the action data structure that indicates the parameters required for the fulfillment of the first request; generate, by the action handler component, an input request based on the open slot of the action data structure; transmit, by the action handler component, the input request to the client computing device; receive, by the natural language processor component, a second input audio signal detected by the sensor of the client computing device in response to the input request rendered at the client computing device; parse, by the natural language processor component, the second input audio signal to identify a parameter; store, by the action handler component, the parameter into the open slot of the action data structure; and transmit, by the action handler component, the action data structure to the service provider device to fulfill the first request.
 40. The system of claim 39, comprising: transmit a form state comprising the parameter in the open slot of the action data structure to the service provider device for validation by the service provider device; receive an updated form state indicating the parameter in the open slot of the action data structure is invalid; and generate a second input request based on the parameter in the open slot of the action data structure being invalid. 